What's New in IT and New World 2019.1 FAQs

A: We’ll provide a tax form MIU patch on 2018.1 in calendar year 2019. At some point in 2020, patching for 2018.1 will slow and eventually cease.

A: No, users will still be in the New World ERP and Tyler Identity databases.

A: Changes are mostly bug/fix in eSuite in this version.

A: Tyler Identity supports Active Directory Federated Services. It also supports Azure AD, however we do not believe we have a New World ERP customer using Azure AD at this point.

A: No, each environment will have a management console. Likewise, if you stack environments on one server, each environment will have a management console with an instanced URL.

A: This gets installed on the App Server and is secured by a user group on the App Server. This allows you to access it from any machine in your network via a web browser. Because of this, you’ll want to make sure the users in that security group are admin types.

A: Windows Server 2019 is not supported at this time. As always, we will continue to look into supporting current and upcoming Microsoft products.

A: For New World ERP, only .Net 4.6.2 was tested on user machines, however we do not believe a breaking change has been introduced for .Net 4.6 on the user machines. The Technical Currency Matrix on Help Central holds full details.

A: We have a white paper we can publish to you that explains the security mechanisms in Deploy. We are working out how to publish this.

A: You will simply not be able to patch. ERP will still be installed on prem regardless of how Deploy is managed. This is a bit different in hosted setups that need a VPN and the internet to access the New World ERP software, but that requirement has existed since hosting was rolled out.

A: Application and eSuite servers will need access to this specific site and port: https://tylerdeployer.tylertech.com:10943

A: TylerDeploy.com’s release is going to occur very soon, within a matter of days. When you request release 2019.1, we’ll ask you who your deployment users are to give you Tyler Deploy access. End users should not be in TylerDeploy.com.

A: Cashiering is now (with the 2019.1 release of Cashiering). TCM is going through Early Adoption with their customers through Tyler Deploy. We are unsure of the CAFR Builder schedule, however the vision of Tyler is all products will go through Tyler Deploy for updates in the near future.

A: Yes, we can add environments for you. This would be worked out with our support group as we don’t want to clutter all customers with extra environments.

A: Yes, the MIU could not do this, but Tyler Deploy does it through a tentacle installed on the DMZ server, likely the eSuite server.

A: Yes, 2019.1 ERP will continue to work with Hub. Our Compatibility Matrix on Help Central holds the detail of what Hub version(s) would work with 2019.1 ERP.

A: Tyler Identity will use a new version in 2019.1 than 2018.1, however you still have to use either TID mode or AD mode, not both.

A: Tyler Identity functions in much the same way in the updated version as the prior version. Users will need to enter their password if they entered it in 2018.1.

A: Yes, when we split 2019.1 from 2018.1 merging, all 2018.1 patching that is done will get done in 2019.1 (if applicable).

A: 2017.1 -> 2019.1 is a direct upgrade path for New World ERP.

A: Yes, the 2019.1 version of Help Central has install documentation for 2019.1 on it. Please note that this site is still in construction mode until GA date.

A: 2019.1 is a landmark release with the implement of Tyler Deploy. It may be a good time to look at this option as getting the foundation right for your Tyler Deploy experience is important.

A: It would take slightly longer to upgrade from 2017.1 than 2018.1. However, at the office, we plan for up to a work day to do an upgrade.

A: The Web API achieves specific functions for us (Utility IVR, Executime, Work Order Interface, etc). It would depend on what is trying to be accomplished here. If it is not a function that we have coded for, likely not.